Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Martin Cech
@martenson
@jmchilton what happened?
Dannon
@dannon
I think Jenkins is rerunning a ton of really, really old builds?
John Chilton
@jmchilton
It won't stop just running tests for old PRs merged months and years ago
"Created Pull Request #4,607 on galaxyproject/galaxy by natefoo () updated at: 9/13/17 1:30 PM SHA: b442113e76fde691577bf14bfd0717fcca166539
Mar 15, 2018 2:15:37 PM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest updatePR"
Nicola Soranzo
@nsoranzo
@Micropathology It's mixed with the main Galaxy log
Martin Cech
@martenson
I don't see any changes on those old PRs, maybe something is changing the commit status there?
Nicola Soranzo
@nsoranzo
Re. Jenkins, maybe it's because I was adding some xref to PR descriptions?
Martin Cech
@martenson
did you add anything to galaxyproject/galaxy#4607 ?
galaxybot
@galaxybot
[mrscribe] Title: Python 3 fixes for set_metadata.py by natefoo · Pull Request #4607 · galaxyproject/galaxy · GitHub (at github.com)
Nicola Soranzo
@nsoranzo
Yes
Sorry
Martin Cech
@martenson
I cannot see it, where is it?
Nicola Soranzo
@nsoranzo
At least I'm done :(
xref. #1715 in the PR description
Martin Cech
@martenson
I see
that makes sense then
Nicola Soranzo
@nsoranzo
It seems this triggers a new build for some reason, stupid Jenkins!
Martin Cech
@martenson
ghprb saw a change and triggered a build because the last one was failed.
it is not that stupid, just the age of the PR and the fact it is merged should prevent it though
Nicola Soranzo
@nsoranzo
Why would a change in the PR description be relevant?
Do you need help in stopping them?
Martin Cech
@martenson
I stopped them
I think the edit on the description might be perceived as a new PR
John Chilton
@jmchilton
I'll research not running on merged PRs - that part seems silly
Nicola Soranzo
@nsoranzo
OK, thanks, sorry for the trouble
John Chilton
@jmchilton
Not your fault - don't worry
Martin Cech
@martenson
^
Micropathology
@Micropathology
@nsoranzo i uninstalled it and reinstalled it, what I am looking for in the log?
natefoo @natefoo appreciates the xrefs
Ghost
@ghost~5772e7e2c2f0db084a206e1b
the output from conda, what packages are being installed etc
Nicola Soranzo
@nsoranzo
I was working on some statistics: 63 PRs (at least partially) concerning Python3 support since December 2015
Philip Mabon
@Takadonet
anyone having issue where in 17.09 or 18.01 where your Data Manger tools are not showing up in the admin Section?
Martin Cech
@martenson
@nsoranzo neat!
@Micropathology it is usually nicer to host longer gists externally and link them
I did it for you here: https://gist.github.com/martenson/5d673c4816738f1757d745063654113b
galaxybot
@galaxybot
[mrscribe] Title: gist:5d673c4816738f1757d745063654113b · GitHub (at gist.github.com)
Nicola Soranzo
@nsoranzo
@Micropathology look for conda create
(which is not there, that's the log for the tool run, not installation)
Tomas
@TKlingstrom

We've made some major improvements in Galaksio to resolve the handling of conditional variables and required values. Currently I am looking for more workflows to test it on. So if anyone wants to test Galaksio or can suggest Galaxy servers with workflows and example data it would be hugely appreciated.

You can read more and get Galaksio from our github (https://github.com/fikipollo/galaksio) or by docker (suggested command: docker run -it -p 8081:80 tklingstrom/galaksio)

galaxybot
@galaxybot
[mrscribe] Title: GitHub - fikipollo/galaksio: An easy-to-use way for running Galaxy workflows. (at github.com)
Nicola Soranzo
@nsoranzo
@dannon I guessed you missed my comment on galaxyproject/galaxy#5708 , I'll open a new PR
Dannon
@dannon
Yeah, it showed up after I clicked merge.
Nicola Soranzo
@nsoranzo
No problem
John Chilton
@jmchilton
@natefoo What can I trade you for machine load logging on stats.galaxyproject.org that includes the Jenkins nodes? Test cases for your upload PR, beer, a Pulsar fix, maybe a memory and I/O constrained datatype sniffing framework?
Ah crap - good catch @nsoranzo. I meant to check the output artifacts on those and see if they duplicated but I forgot
Nicola Soranzo
@nsoranzo
Does my solution make sense?
I think decorator are applied from last to first
Dannon
@dannon
Yeah, outside in.
Well, wraps from the top to bottom (or outside in). Order of execution is actually the opposite, inside-out. RIght?
John Chilton
@jmchilton
It does make sense for the test_run_data - I would expect the jupyter test to skip from the inside because the viz is not available - I tried to implement that - but I guess it is being skipped because it is marked flakey instead which is masking the inner error