Wow, that video is pretty damning.
(a) Even though the driver was getting a warning to put his hands on the wheel, the car should NOT continue driving forward and piloting itself at all with no driver response and insufficient certainty to continue navigating itself.
(b) There was a very obvious hard barrier right in front of the car. Why didn't the collision avoidance detect it and halt the car?
(c) The car was clearly "pulled" to the left by the bright exit lane stripe and missing highway-side stripe.
Simply following stripes seems an absurdly primitive and unreliable technique to me. The fact that the car could be "distracted" this way suggests to me that it isn't getting (or making good use of) a lot of information that should be available to it-- like the behavior of other traffic, the presence of other obstacles and roadside geometry (like the ignored barrier, which was on a collision path), the trajectory on previous trips (and any conclusions drawn then under better conditions), the road sign which indicated a fork (and which was also itself on a direct collision path), the crosswise striping in between the two forks which the car was driving over, and the striping on the other edge of the lane, and the lanes beyond, which followed the correct trajectory.
Each of those things is a significant clue as to the real path of the lane, and are all machine-detectable and processable pieces of information. Even with nontrivial uncertainty about each of them, the totality of information, IMO, should be more than enough to clearly discern the correct lane, especially if efficiently used-- Kalman filter-like information synthesis can take a lot of very uncertain information and synthesize a very certain picture.
Instead the machine ignored the holistic picture and "target fixated" on the stripe. This apparently has a disappointingly long way to go before it is a reliable system.