...
[16:16:21 CST(-0600)] <pandisaurus> and bar.channel fails another time
[16:16:34 CST(-0600)] <EricDalquist1> that is very strange
[16:16:39 CST(-0600)] <pandisaurus> where foo.channel and bar.channel are completely arbitrary because it could be any of the channels
[16:16:43 CST(-0600)] <EricDalquist1> yeah
[16:16:48 CST(-0600)] <pandisaurus> and sometimes it just goes through all of them claiming successful
[16:17:25 CST(-0600)] <EricDalquist1> I'm just about to sign off for the day … could you create a jira issue at issues.jasig.org and paste in the full output of a failed run?
[16:17:31 CST(-0600)] <EricDalquist1> that would help in tracking down the problem
[16:17:40 CST(-0600)] <pandisaurus> I'll note, it says "INFO Importing 104 files of type <channel-definition script="classpath://org/jasig/portal/io/import-channel_v3-2.crn"> " then it does not say upgraded 104 times
[16:17:55 CST(-0600)] <EricDalquist1> ok, that sounds correct
[16:18:14 CST(-0600)] <EricDalquist1> even better if you can also attach the .channel file that failed in the example you post
[16:18:21 CST(-0600)] <EricDalquist1> I realize it is different channel files each time
[16:18:28 CST(-0600)] <EricDalquist1> but having the correlation for one failed run could help
[16:18:56 CST(-0600)] <pandisaurus> I can do that no problem, its just odd
[16:19:06 CST(-0600)] <EricDalquist1> I agree
[16:19:21 CST(-0600)] <pandisaurus> what determines whether it says 'upgraded' next to the channel or not?
[16:19:58 CST(-0600)] <pandisaurus> since I have you here
[16:20:35 CST(-0600)] <EricDalquist1> it should say it for all of them
[16:20:43 CST(-0600)] <EricDalquist1> since you are importing .channel files from 3.2
[16:20:57 CST(-0600)] <EricDalquist1> the XML file has to be transformed into the 4.0 format
[16:20:59 CST(-0600)] <EricDalquist1> and then imported
[16:21:10 CST(-0600)] <EricDalquist1> that transform step is what prints out the upgraded message
[16:21:54 CST(-0600)] <pandisaurus> I'm showing 24 "upgraded" messages, but it says it found 104 files to import (104 should be accurate) is there a way to see what files its skipping and why?
[16:22:08 CST(-0600)] <EricDalquist1> is that after a failure?
[16:22:16 CST(-0600)] <pandisaurus> no I'm counting when its successful
[16:22:19 CST(-0600)] <EricDalquist1> hrm
[16:22:23 CST(-0600)] <EricDalquist1> that sounds like a bug
[16:22:35 CST(-0600)] <EricDalquist1> you should be seeing either the same numbers all the way through
[16:22:40 CST(-0600)] <EricDalquist1> or it should fail with a reason
[16:22:49 CST(-0600)] <EricDalquist1> stuff shouldn't get silently ignored
[16:23:39 CST(-0600)] <pandisaurus> hmmm, that's troublesome because it is silently ignoring. "git checkout" just updates to the most current version of the trunk right? If I'm not specifying a branch?
[16:25:16 CST(-0600)] <EricDalquist1> sorry
[16:25:40 CST(-0600)] <EricDalquist1> "git checkout branch-name" checks out the specified branch
[16:25:41 CST(-0600)] <EricDalquist1> locally
[16:25:50 CST(-0600)] <EricDalquist1> to updates to the branch you are currently on
[16:25:57 CST(-0600)] <EricDalquist1> do "git pull"
[16:26:18 CST(-0600)] <EricDalquist1> which is a shortcut for doing:
[16:26:18 CST(-0600)] <EricDalquist1> git fetch
[16:26:19 CST(-0600)] <EricDalquist1> git merge origin/current-branch-name
[16:26:34 CST(-0600)] <EricDalquist1> you can determine your current branch via "git status"
[16:26:41 CST(-0600)] <EricDalquist1> have to run though