Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Dannon
@dannon
Oh weird.
Nicola Soranzo
@nsoranzo
@jmchilton galaxyproject/galaxy#5701 seems to properly save the available artifacts, correct?
John Chilton
@jmchilton
galaxybot
@galaxybot
[mrscribe] Title: Artifacts of docker-selenium #1695 : /1695-test-errors [Jenkins] (at jenkins.galaxyproject.org)
Nicola Soranzo
@nsoranzo
Just wanted to double check with you, merging now.
John Chilton
@jmchilton
Thanks for the help with that by the way
Nicola Soranzo
@nsoranzo
Sure thing
Ghost
@ghost~5772e7e2c2f0db084a206e1b
@Micropathology what command did you use to install unicycler ?
Can you look at the installation log for prokka ?
Nate Coraor
@natefoo
is static/style/blue/base.css supposed to exist in dev?
Dannon
@dannon
Yes.
Only static/scripts were dropped. We left style since it changes so much less often.
(and is much more of a pain to add style and the various artifacts back in release branches)
Nate Coraor
@natefoo
ah
it changes all the time when developing which is a little annoying
Dannon
@dannon
Ideally we drop that, along with even more stuff, down the road though as the auto-building/etc gets a real test and seems to be robust enough.
It should only change if someone in a commit before you forgot to add it, or if you're changing styles?
Nate Coraor
@natefoo
i'm not sure why it differs since i'm not changing ... yeah.
could be due to different versions of the build tools
Dannon
@dannon
Possible. I'm overhauling that a lot right now in my bs4 branch, hopefully a few more steps towards it being robust enough to drop.
Nate Coraor
@natefoo
cool
Dannon
@dannon
(it almost looks like Galaxy again!)
Nate Coraor
@natefoo
haha
John Chilton
@jmchilton
Ugh - it won't stop. @martenson do you know how to save Jenkins?
Micropathology
@Micropathology
@mvdbeek where is the tool install log?
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