-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 1312 tag repos #1321
Issue 1312 tag repos #1321
Conversation
added capability to checkout a specific branch for testdata repo fix #1312
@doutriaux1 we would have -s ours when we bring this change to master. |
Cloning into 'VTK'... |
you merged it in before I applied the tag I think, can you try again, the tag should be on VTK since last night |
I didn't. The error is from buildbot machines. When you pushed a branch buildbot slaves ran the build. |
I reset the builds. Buildbot will start a build every time you push a change even if there isn't a PR for it yet. |
I see. Well we're good now, the tags are in place. Can we restart the test? |
I already did. Here is one of the results. |
oh god... Looks like the tag point for VTK is wrong, let me double check, I might have tagged master rather than uvcdat-master.... Doh! |
@jbeezley how to do you restart the buildbot? I moved the tag point. |
You have to be connected to our local network for the moment. I think we are working on exposing the buildbot interface, but for now just ping me. |
yup, I am talking to the sys admins here to see if we can expose it to LLNL or allow @doutriaux1 to login to that machine somehow. |
@jbeezley or @aashish24 can you restart it then for this time, the tag on VTK is correct now. |
I did, they are in the queue. Patience, «petit scarabée». |
I loved that show! And I definitely need to learn the mysterious ways of the path to patience.... |
For some reason garant has lot more tests failing. @jbeezley do you know why? |
@doutriaux1 we still need to merge this branch right? |
@doutriaux1 @aashish24 it seems 2.2.0rc1 is what has been issued the DOI at zenodo and not 2.2.0.. It might be good to get the additional tweaks into master and then move the 2.2.0 tag point? |
@doutriaux1 @aashish24 it seems that the correct 2.2.0 zenodo DOI is 10.5281/zenodo.17633 - I'll update in PR #1334 (updated) |
can't believe i didn't notice @aashish24 did merge this one in master not release before tagging.... Well merging now... |
@doutriaux1 I didn't merge this one. In face this branch should go last in release. |
338ff31 Merge pull request #1328 from UV-CDAT/issue1212_durack1_Spyder2 |
yes but you merged in into master where it didn't really need to go. Then I thought you merged it in release and TAGGED release assuming it was in.... |
@aashish24 pedantic point, but your info contained in the README.md for https://github.com/UV-CDAT/uvcdat/tree/2.2.0 is out of sync with the tag.. |
@aashish24 @dlonie @chaosphere2112 please review